翻訳と辞書
Words near each other
・ Wildenfels
・ Wildengundkopf
・ Wildboarclough
・ Wildboys (comics)
・ Wildboyz
・ WildBrain
・ WildC.A.T.s/Aliens
・ WildC.A.T.s/X-Men
・ Wildcard (album)
・ Wildcard (comics)
・ Wildcard (Java)
・ Wildcard (Pennywise EP)
・ Wildcard / A Word from the Wise
・ Wildcard certificate
・ Wildcard character
Wildcard DNS record
・ Wildcard mask
・ Wildcat
・ WildCat (Cedar Point)
・ Wildcat (comics)
・ Wildcat (disambiguation)
・ Wildcat (film)
・ Wildcat (Hersheypark)
・ Wildcat (Lake Compounce)
・ Wildcat (musical)
・ WildCat (roller coaster)
・ Wildcat (short story)
・ Wildcat (Yolanda Montez)
・ Wildcat 12
・ Wildcat APC


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Wildcard DNS record : ウィキペディア英語版
Wildcard DNS record
A wildcard DNS record is a record in a DNS zone that will match requests for non-existent domain names. A wildcard DNS record is specified by using a "
*" as the leftmost label (part) of a domain name, e.g.
*.example.com
. The exact rules for when a wild card will match are specified in RFC 1034, but the rules are neither intuitive nor clearly specified. This has resulted in incompatible implementations and unexpected results when they are used.
==Definitions of DNS wildcards==
A wildcard DNS record in a zone file looks similar to this example:

*.example.com. 3600 IN MX 10 host1.example.com.
This wildcard DNS record will cause DNS lookups on domain names ending in example.com that do not exist to have MX records synthesized for them. So, a lookup for the MX record for somerandomname.example.com would return an MX record pointing to host1.example.com.
Wildcards in the DNS are much more limited than other wildcard characters used in other computer systems. Wildcard DNS records have a single "
*" (asterisk) as the leftmost DNS label, such as
*.example.com
. Asterisks at other places in the domain will not work as a wildcard, so neither
*abc.example.com
nor abc.
*.example.com
work as wildcard DNS records. Moreover, the wildcard is matched only when a domain does not exist, not just when there are no matching records of the type that has been queried for. Even the definition of "does not exist" as defined in the search algorithm of RFC 1034 section 4.3.2 can result in the wild card not matching cases that one might expect with other types of wildcards.
The original definition of how a DNS wildcard behaves is specified in RFC 1034 sections 4.3.2 and 4.3.3, but only indirectly by certain steps in a search algorithm and as a result, the rules are neither intuitive nor clearly specified. As a result, 20 years later, RFC 4592, "The Role of Wildcards in the Domain Name System" was written to help clarify the rules.
To quote RFC 1912, "A common mistake is thinking that a wildcard MX for a zone will apply to all hosts in the zone. A wildcard MX will apply only to names in the zone which aren't listed in the DNS at all." That is, if there is a wild card MX for
*.example.com
, and an A record (but no MX record) for www.example.com, the correct response (as per RFC 1034) to an MX request for www.example.com is "no error, but no data"; this is in contrast to the possibly expected response of the MX record attached to
*.example.com
.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Wildcard DNS record」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.